@foolmoron I've run this with a locally running choreographer. it connects to the choregrapher which seems to return the needed key but the client throws some error. do you have everything you need to run the choreographer locally? we could also deploy the endpoint to our staging server without too much trouble.

@foolmoron I've run this with a locally running choreographer. it connects to the choregrapher which seems to return the needed key but the client throws some error. do you have everything you need to run the choreographer locally? we could also deploy the endpoint to our staging server without too much trouble.

I did find how to get the local choreo working (there are 2 .env files that need the API URL changed) but yeah there's some client errors I haven't figured out. Do you think you could take a look and see if you can fix it faster than I could?

@foolmoron Looking into it!

@foolmoron Hey I just put 45 minutes into debugging. I looked for errors in the logic of the file itself and just tried commenting out various pieces to see where the issue might be coming from.

It's coming from this:

final audioRecorderStartFuture =
            await _audioRecorderStream!.startRecorder(
          toStream: streamBytes.sink,
          codec: Codec.pcm16,
          numChannels: 1,
          sampleRate: samplingRateTranscription,
          bitRate: samplingRateTranscription,
        );

I've got a meeting now. I think I'd need to go deep into FlutterSoundRecorder to see if there was some error in the setup sequence. That is my suspicion. Or maybe it's incompatible with AudioRecorder.

@wcjord Hm ok, might need a bigger refactor to use just one recorder

@foolmoron That would probably make sense.